Update AWS CLI to v2#287
Merged
Merged
Conversation
We are wanting to use AWS CLI features that are only available in v2.¹ In the last attempt to upgrade AWS, the main blocker was the fact that `AWS_DEFAULT_REGION` is now required.² For Nextstrain workflows, this is now mitigated by the fact that the shared pathogen-repo-build GH Action workflow sets the envvar.³ We have also been using awscli >= 2 in conda-base without any issues.⁴ ¹ <nextstrain/infra#72 (comment)> ² <#214 (comment)> ³ <https://github.com/nextstrain/.github/blob/5b32fb95e6613823e9cc12e06beec164503980f4/.github/workflows/pathogen-repo-build.yaml#L303> ⁴ <https://github.com/nextstrain/conda-base/blob/dc99d69d91420da760519d54be051452744351f4/src/meta.yaml#L54>
Contributor
Author
|
Will merge and release this tomorrow if there's no feedback. |
victorlin
approved these changes
Jun 22, 2026
victorlin
left a comment
Member
There was a problem hiding this comment.
Checked PR image:
$ nextstrain shell --image nextstrain/base:branch-aws-v2 ~/tmp -c 'aws --version'
Entering the Nextstrain runtime (docker)
…
aws-cli/2.35.7 Python/3.14.5 Linux/6.12.76-linuxkit exe/aarch64.debian.12
Comment on lines
+214
to
+215
| # Using `xx-info march` to translate amd64 -> x86_64 and arm64 -> aarch64 | ||
| # based on https://github.com/docker/buildx/discussions/2001 |
Member
There was a problem hiding this comment.
Nice find, this can probably replace builder-scripts/target-triple elsewhere.
| # Using `xx-info march` to translate amd64 -> x86_64 and arm64 -> aarch64 | ||
| # based on https://github.com/docker/buildx/discussions/2001 | ||
| RUN XX_MARCH=$(xx-info march) \ | ||
| && curl -fsSL --proto '=https' "https://awscli.amazonaws.com/awscli-exe-linux-${XX_MARCH}.zip" -o "awscliv2.zip" \ |
Member
There was a problem hiding this comment.
We have also been using awscli >= 2 in conda-base without any issues.
I'm guessing there's a good amount of AWS CLI usage not captured by pathogen repo CI (e.g. upload-to-s3), but we can just merge and monitor.
Contributor
Author
There was a problem hiding this comment.
No obvious errors in today's pathogen workflows, will continue to monitor the rest of the week.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
We are wanting to use AWS CLI features that are only available in v2.¹ In the last attempt to upgrade AWS, the main blocker was the fact that
AWS_DEFAULT_REGIONis now required.² For Nextstrain workflows, this is now mitigated by the fact that the shared pathogen-repo-build GH Action workflow sets the envvar.³ We have also been using awscli >= 2 in conda-base without any issues.⁴¹ nextstrain/infra#72 (comment)
² #214 (comment)
³ https://github.com/nextstrain/.github/blob/5b32fb95e6613823e9cc12e06beec164503980f4/.github/workflows/pathogen-repo-build.yaml#L303
⁴ https://github.com/nextstrain/conda-base/blob/dc99d69d91420da760519d54be051452744351f4/src/meta.yaml#L54
Related issue(s)
Resolves #216
Checklist
Update changelog